Structured Headings
Domain Message Specification

PatientUniversal Tabular View

COCD_TP145201GB02
PatientRole

This template class constrains the CDA PatientRole class.

The purpose of this template is to allow patient information that would normally be retrieved from the Personal Demographics Service (PDS) to be carried in a CDA document. This is to allow sending and receiving systems which do not have access to PDS to be able to identify the patient using a wider range of information than just NHS number.

This template does not support the full patient information obtainable from PDS only the information that is supported by CDA. This subset of patient information is sufficient for use in CDA document exchanges.

This template also constrains the patient information supported by CDA to make it suitable for NHS use.
Used by:
[1..1] [M] classCode (CS { CNE: RoleClass } )
{ Fixed="PAT" }

Model Attribute Description

The HL7 attribute classCode uses a code to describe this class as a role of patient.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PAT".
[0..4] addr (SET<AD>)

Model Attribute Description

The HL7 attribute addr is used to carry one or more addresses for the patient.

The HL7 attribute addr allows structured and unstructured addresses to be carried. Only structured addresses are recommended to be used.

Implementation in XML Instance

There are a number of forms of structured address. The three shown here are the recommended formats for patient addresses, they are listed in no particular order.

The XML element addr is populated as follows:

When using the structured address in the style of PDS the XML element addr shall contain five XML elements streetAddressLine:

  • The first XML element streetAddressLine shall contain the premises name
  • The second XML element streetAddressLine shall contain the number and thoroughfare
  • The third XML element streetAddressLine shall contain the locality
  • The fourth XML element streetAddressLine shall contain the post town
  • The fifth XML element streetAddressLine shall contain the county

The first XML element streetAddressLine or the second XML element streetAddressLine and the fourth XML element streetAddressLine are mandatory to be populated.

  • The XML element postalCode can be used to carry a postcode
  • The XML element addressKey can be used to carry a PAF key

When using the fully structured address format then the XML element addr shall be populated as follows:

  • The XML element houseNumber shall contain the house/building number or name
  • The XML element streetName shall contain the street name
  • The XML element city shall contain the city name
  • The XML element county shall contain the county
  • The XML element country shall contain the country name
  • The XML element postalCode shall contain the postcode
  • The XML element addressKey shall contain the address key

Note that unpopulated XML elements should not be present.

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included.

  • The first XML element streetAddressLine shall contain the first address line
  • The second XML element streetAddressLine shall contain the second address line
  • The third XML element streetAddressLine shall contain the third address line
  • and so on ....

Note that unpopulated XML elements should not be present.

The XML element addr also allows an XML attribute use and this should be used to further define the patient address type when required. Only the use values listed below are recommended to be used for patient addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - A temporary address; may be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
Postal address - Used to send mail.
H
Home address - The person's home address; attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.
HP
The primary home address - An address to reach a person after business hours.
HV
A vacation home - An address to reach a person while on vacation.

When the XML attribute use of the XML element addr contains the value "PHYS" then the following two XML elements of the XML element addr may be populated.

  • The XML element desc of the XML element addr may contain a description of the address; this may be used for things like directions for the address.
  • The XML element additionalLocator of the XML element addr may contain additional location information such as longitude and latitude coordinates.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times for an address:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours of an office for a work address
    • Using dates for indicating a contact address is only for a certain period of time.
  • A start time only to indicate when the contact address is valid from.
  • An end time only to indicate that the contact address is only valid until a certain date.
[1..2] [M] id (SET<II>)

Model Attribute Description

The HL7 attribute id enables the identification of the patient using the NHS number, or a local identifier if the NHS number is not available. This attribute has been extended for NHS use to allow the status of the NHS number to also be stated.

Implementation in XML Instance

There must be either one or two instances of id.

  • The first instance of id must contain information related to the patient's NHS Number
  • The second instance of id may contain information related to a local patient identifier

For a verified NHS Number:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.4.1"
  • The XML attribute extension shall contain the 10 digit NHS number.
  • The XML attribute patientIdStatus shall contain the value "01".

For an unverified NHS Number:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.3.2.4.18.23"
  • The XML attribute extension shall contain the 10 digit NHS number.
  • The XML attribute patientIdStatus shall contain one of the following values to indicate the status of the included NHS number:
Code Description
02 Number present but not traced
03 Trace required
04 Trace attempted - No match or multiple match found
05 Trace needs to be resolved - (NHS Number or patient detail conflict)
06 Trace in progress
08 Trace postponed (baby under six weeks old)

When the NHS Number is not included then:

  • The XML attribute patientIdStatus shall contain the value "07"
  • The XML attributes root, extension and the assigningAuthorityName should not be populated

A local identifier for the patient may also be included in the second instance of id as below:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.3.2.4.18.24"
  • The XML attribute extension shall contain the local patient identifier
  • The XML attribute assigningAuthorityName shall contain the assigning organisation in the format of ODSCode:ODSName,

for example: assigningAuthorityName="RA9:SOUTH DEVON HEALTHCARE NHS TRUST"

[0..*] telecom (SET<TEL>)

Model Attribute Description

The HL7 Attribute telecom specifies contact details for the patient in the form of telephone numbers, fax numbers and email addresses.

Implementation in XML Instance

The XML value attribute of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.

  • For a telephone number the actual telephone number would be prefixed with tel:
  • For a fax number the actual fax number would be prefixed with fax:
  • For an email address the actual email address would be prefixed with mailto:

The XML attribute use of the XML element telecom may be used to give further information about the type of contact details contained in the XML attribute value. Only the use values listed below are recommended to be used for the patient contact details:

Code Definition
AS Answering service - an automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.
EC
Emergency contact - A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.
H
Home - A communication address at a home, attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.
HP
Home primary - the primary contact to reach a person after business hours.
HV
Home vacation - A vacation home, to reach a person while on vacation.
WP
Work place - An office address. First choice for business related contacts during business hours
PG
Pager - A paging device suitable to solicit a callback or to leave a very short message.
MC
Mobile contact - A telecommunication device that moves and stays with its owner. May have characteristics of all other use codes, suitable for urgent matters, not the first choice for routine business.

The XML element useablePeriod of the XML element telecom may be used to indicate when the contact details given are valid, for example to indicate that a telephone number is only for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:

  • A point in time when the contact details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours of an office for work contacts
    • Using dates for indicating a contact is only for a certain period of time.
  • A start time only to indicate when the contact details are valid from.
  • An end time only to indicate that the contact details are only valid until a certain date.
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#PatientRole" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#PatientRole"
[1..1] [M] patientPatient (Patient)

A link to the patient class.

[0..1] providerOrganization (Organization)

A link to the organisation class that provides the care.

Patient

This template class constrains the CDA Patient class.

This class details information about the person who is the patient.

Used by: PatientRole
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="PSN" }

Model Attribute Description

The HL7 attribute classCode describes this class as a person.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PSN".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of a person.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[1..1] [R] administrativeGenderCode (CV { CNE:Sex } )

Model Attribute Description

The HL7 attribute administrativeGenderCode uses a code from the Sex vocabulary to indicate the gender of the patient.

This code is for administrative purposes only and does not imply a particular genetic or physical sex.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element administrativeGenderCode as follows:

  • The XML attribute code shall contain a code from the Sex vocabulary
  • The XML attribute codeSystem shall contain the fixed OID "2.16.840.1.113883.2.1.3.2.4.16.25"
  • The XML attribute displayName shall carry the description associated with the code in the Sex vocabulary.
  • When no patient gender code is available to the sending system to then an appropriate XML attribute nullFlavor may be used to populate the XML element administrativeGenderCode. The recommended values for the XML attribute nullFlavor are listed below:

    nullFlavor Definition
    UNK Unknown - A proper value is applicable, but not known
    ASKU Asked but unknown - Information was sought but not found (e.g., patient was asked but didn't know)
    NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
    NASK Not asked - This information has not been sought (e.g. patient was not asked)
    MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

    There may be an alternate mechanism for gaining access to this information.

[1..1] [R] birthTime (TS)

Model Attribute Description

The HL7 attribute birthTime specifies the patient's date of birth.

Implementation in XML Instance

The XML attribute value of the XML element birthTime shall be populated a time stamp in the format yyyymmddhhmm where:

  • yyyy is the year
  • mm is the month
  • dd is the day
  • hh is the hour
  • mm is the minute

At least the year must be present.

The XML attribute value of the XML element birthTime should be populated to the level of detail that is available on the sending system.

When no patient date of birth is available to the sending system to then an appropriate XML attribute nullFlavor may be used to populate the XML element birthTime. The recommended values for the XML attribute nullFlavor are listed below:

nullFlavor Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found (e.g., patient was asked but didn't know)
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought (e.g. patient was not asked)
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[0..1] deceasedInd (BL)

Model Attribute Description

A flag used to indicate whether the patient is deceased.

This is an NHS localisation extension to CDA which has a separate namespace.

Implementation in XML Instance

The XML attribute value of the XML element deceasedInd should carry true or false.

The XML element deceasedInd can carry the XML attribute nullFlavor instead of a value when the deceased status is unclear or not known and the fact is required to be asserted.

The recommended values for the attribute nullFlavor are listed below:

nullFlavor
Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[0..1] deceasedTime (TS)

Model Attribute Description

The HL7 attribute deceasedTime specifies the patient's date of death.

This is an NHS localisation extension to CDA which has a separate namespace.

Implementation in XML Instance

The XML attribute value of the XML element deceasedTime shall be populated a time stamp in the format yyyymmddhhmm where:

  • yyyy is the year
  • mm is the month
  • dd is the day
  • hh is the hour
  • mm is the minute

At least the year must be present.

The XML attribute value of the XML element deceasedTime should be populated to the level of detail that is available on the sending system.

When the patient's date of death is expected, but cannot be sent because there is no information to populate the XML element deceasedTime available on the sending system, then an XML attribute nullFlavor of the XML element deceasedTime can be used. The recommended values for the XML attribute nullFlavor are listed below:

nullFlavor Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found (e.g. patient was asked but didn't know)
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought (e.g., patient was not asked)
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[0..1] ethnicGroupCode (CV { CWE:Ethnicity } )

Model Attribute Description

The ethnic grouping the patient affiliates themselves to.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element ethnicGroupCode as follows:

When the default NHS Data Dictionary codes are used then:

  • The XML attribute code shall contain a code from the Ethnicity vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.16.81"
  • The XML attribute displayName shall carry the description associated with the code in the Ethnicity vocabulary

When the extended set of codes are required then:

  • The XML attribute code shall contain a code from the EthnicCategory vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.16.6"
  • The XML attribute displayName shall carry the description associated with the code in the EthnicCategory vocabulary

Note, the values for both these vocabularies can be accessed via the link on the left hand side.


[0..1] maritalStatusCode (CV { CWE:MaritalStatus } )

Model Attribute Description

The martial status of the patient.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element maritalStatusCode as follows:

The XML element maritalStatusCode is populated as below:

  • The XML attribute code shall contain a code from the MaritalStatus vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.16.82"
  • The XML attribute displayName shall carry the description associated with the code
[0..1] multipleBirthInd (BL)

Model Attribute Description

A flag used to indicate whether the patient was part of a multiple (2 or more) birth.

This is an NHS localisation extension to CDA which has a separate namespace.

Implementation in XML Instance

The XML attribute value of the XML element multiplebirthInd carries true or false.

The XML element multipleBirthInd can carry the XML attribute nullFlavor instead of a value when the multiple birth status is unclear or not known and the fact is required to be asserted.

The recommended values for the attribute nullFlavor are listed below:

nullFlavor
Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.


[0..1] multipleBirthOrderNumber (INT)

Model Attribute Description

The order of the patient's birth as part of a multiple birth.

This is an NHS localisation extension to CDA which has a separate namespace.

Implementation in XML Instance

The XML attribute value of the XML element multiplebirthOrderNumber carries an integer to indicate the birth order of the patient as part of a multiple birth. For example, if the patient is a twin and was the second to be born, the XML attribute value would be 2.

The XML element multipleBirthOrderNumber can carry the XML attribute nullFlavor instead of a value when the multiple birth order number is unclear or not known and the fact is required to be asserted.

The recommended values for the attribute nullFlavor are listed below

nullFlavor
Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[1..*] [R] name (SET<PN>)

Model Attribute Description

The HL7 attribute name provides names associated with the person who is the patient.

Implementation in XML Instance

The Person Name Structured with optional Use and optional Valid Time flavour of the PN data type is the recommended format for the patient's name. This information is carried in the XML element name as follows:

  • The XML element prefix should contain the patient's title
  • The XML element given should contain the patient's forenames; there can be as many occurrences of the XML element as required
  • The XML element family should contain the patient's surname
  • The XML element suffix may contain any suffix for the patient

Additionally the XML attribute use of the XML element name should be used to indicate the type of name; the recommended codes to be used are listed below:

Note some of the codes listed are NHS extensions, these are marked with an *

Code Definition
L
Legal
A
Artist / stage
I
Indigenous/Tribal
R
Religious
PREVIOUS-BIRTH *
Birth name
PREVIOUS-MAIDEN *
Maiden name
PREVIOUS-BACHELOR *
Bachelor name
PREVIOUS *
Other previous name
PREFERRED *
Preferred name

Additionally the XML element validTime of the XML element name may be used to indicate the time when the name is valid/was valid for the patient, some uses are shown below:

  • A point in time when the name details are known to be valid
  • A start and end time
    • To represent the period of time the patient is/was known by this name
  • A start time only to indicate when the name is/was valid from for the patient
  • An end time only to indicate that the name is/was only valid for the patient until a certain date

When no patient name is available to the sending system to then an appropriate XML attribute nullFlavor may be used to populate the XML element name. The recommended values for the XML attribute nullFlavor are listed below:

nullFlavor Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found (e.g., patient was asked but didn't know)
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought (e.g. patient was not asked)
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[0..1] religiousAffiliationCode (CV { CNE:ReligiousAffiliationSnCT } )

Model Attribute Description

The religious affiliation of the patient.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element religiousAffiliationCode as follows:

When the HL7 ReligiousAffiliationSnCT vocabulary is used then:

  • The XML attribute code shall contain a code from the ReligiousAffiliationSnCT vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.15"
  • The XML attribute displayName shall carry the displayName associated with the code. It is recommended that the preferred term is used to populate this attribute.

[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#patientPatient" }

Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:

  • The root attribute is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The extension attribute is fixed to "COCD_TP145201GB02#patientPatient
[0..1] birthplace (Birthplace)
A link to the birthplace.
[0..1] guardian (Guardian)
A link to the guardian.
[0..*] languageCommunication (LanguageCommunication)
A link to LanguageCommunication class.
Guardian

This template class constrains the CDA Guardian class.

This class is used to carry information about the patient's guardian, where the guardian maybe a person or an organisation.

Used by: Patient
[1..1] [M] classCode (CS { CNE: RoleClass } )
{ Fixed="GUARD" }

Model Attribute Description

The HL7 attribute classCode describes this class as a guardian role.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "GUARD".
[0..4] addr (SET<AD>)

Model Attribute Description

The HL7 attribute addr is used to carry one or more addresses for the guardian.

The HL7 attribute addr allows structured and unstructured addresses to be carried. Only structured addresses are recommended to be used.

Implementation in XML Instance

There are a number of forms of structured address. The three shown here are the recommended formats for guardian addresses, they are listed in no particular order.

The XML element addr is populated as follows:

When using the structured address in the style of PDS the XML element addr shall contain five XML elements streetAddressLine:

  • The first XML element streetAddressLine shall contain the premises name
  • The second XML element streetAddressLine shall contain the number and thoroughfare
  • The third XML element streetAddressLine shall contain the locality
  • The fourth XML element streetAddressLine shall contain the post town
  • The fifth XML element streetAddressLine shall contain the county

The first XML element streetAddressLine or the second XML element streetAddressLine and the fourth XML element streetAddressLine are mandatory to be populated.

  • The XML element postalCode can be used to carry a postcode
  • The XML element addressKey can be used to carry a PAF key

When using the fully structured address format then the XML element addr shall be populated as follows:

  • The XML element houseNumber shall contain the house/building number or name
  • The XML element streetName shall contain the street name
  • The XML element city shall contain the city name
  • The XML element county shall contain the county
  • The XML element country shall contain the country name
  • The XML element postalCode shall contain the postcode
  • The XML element addressKey shall contain the address key

Note that unpopulated XML elements should not be present.

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included.

  • The first XML element streetAddressLine shall contain the first address line
  • The second XML element streetAddressLine shall contain the second address line
  • The third XML element streetAddressLine shall contain the third address line
  • and so on ....

Note that unpopulated XML elements should not be present.

The XML element addr also allows an XML attribute use and this should be used to further define the guardian address type when required. Only the use values listed below are recommended to be used for guardian addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - A temporary address; may be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
Postal address - Used to send mail.
H
Home address - The person's home address; attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.
HP
The primary home address - An address to reach a person after business hours.
HV
A vacation home - An address to reach a person while on vacation.

When the XML attribute use of the XML element addr contains the value "PHYS" then the following two XML elements of the XML element addr may be populated.

  • The XML element desc of the XML element addr may contain a description of the address; this may be used for things like directions for the address.
  • The XML element additionalLocator of the XML element addr may contain additional location information such as longitude and latitude coordinates.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times for an address:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours of an office for a work address
    • Using dates for indicating a contact address is only for a certain period of time.
  • A start time only to indicate when the contact address is valid from.
  • An end time only to indicate that the contact address is only valid until a certain date.
[0..1] code (CE { CWE:GuardianRoleType } )

Model Attribute Description

The HL7 attribute code uses a code from the GuardianRoleType vocabulary to describe the relationship between the patient and the named person.

Implementation in XML Instance

The Coded Plain flavour of the Coded Value (CV) data type shall be used to carry this information in the XML element code as follows:

  • The XML attribute code shall contain a code from the GuardianRoleType vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.16.454"
  • The XML attribute displayName shall carry the name associated with the code

[0..*] id (SET<II>)

Model Attribute Description

The HL7 attribute id enables the identification of the guardian using the NHS number, or a local identifier if the NHS number is not available. This attribute has been extended for NHS use to allow the status of the NHS number to also be stated.

Implementation in XML Instance

There must be either one or two instances of id.

  • The first instance of id must contain information related to the guardian's NHS Number
  • The second instance of id may contain information related to a local identifier for the guardian

For a verified NHS Number:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.4.1"
  • The XML attribute extension shall contain the 10 digit NHS number.
  • The XML attribute patientIdStatus shall contain the value "01".

For an unverified NHS Number:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.3.2.4.18.23"
  • The XML attribute extension shall contain the 10 digit NHS number.
  • The XML attribute patientIdStatus shall contain one of the following values to indicate the status of the included NHS number:
Code Description
02 Number present but not traced
03 Trace required
04 Trace attempted - No match or multiple match found
05 Trace needs to be resolved - (NHS Number or guardian to detail conflict)
06 Trace in progress
08 Trace postponed (baby under six weeks old)

When the NHS Number is not included then:

  • The XML attribute patientIdStatus shall contain the value "07"
  • The XML attributes root, extension and the assigningAuthorityName should not be populated

A local identifier for the guardian may also be included in the second instance of id as below:

  • The XML attribute root shall contain the OID "2.16.840.1.113883.2.1.3.2.4.18.24"
  • The XML attribute extension shall contain the local identifier for the guardian
  • The XML attribute assigningAuthorityName shall contain the assigning organisation in the format of ODSCode:ODSName,

for example: assigningAuthorityName="RA9:SOUTH DEVON HEALTHCARE NHS TRUST"

Note, where the guardian is an organisation this attribute is not used.

[0..*] telecom (SET<TEL>)

Model Attribute Description

The HL7 Attribute telecom specifies contact details for the guardian in the form of telephone numbers, fax numbers and email addresses.

Implementation in XML Instance

The XML value attribute of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.

  • For a telephone number the actual telephone number would be prefixed with tel:
  • For a fax number the actual fax number would be prefixed with fax:
  • For an email address the actual email address would be prefixed with mailto:

The XML attribute use of the XML element telecom may be used to give further information about the type of contact details contained in the XML attribute value. Only the use values listed below are recommended to be used for the guardian contact details:

Code Definition
AS Answering service - an automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.
EC
Emergency contact - A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.
H
Home - A communication address at a home, attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.
HP
Home primary - the primary contact to reach a person after business hours.
HV
Home vacation - A vacation home, to reach a person while on vacation.
WP
Work place - An office address. First choice for business related contacts during business hours
PG
Pager - A paging device suitable to solicit a callback or to leave a very short message.
MC
Mobile contact - A telecommunication device that moves and stays with its owner. May have characteristics of all other use codes, suitable for urgent matters, not the first choice for routine business.

The XML element useablePeriod of the XML element telecom may be used to indicate when the contact details given are valid, for example to indicate that a telephone number is only for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:

  • A point in time when the contact details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours of an office for work contacts
    • Using dates for indicating a contact is only for a certain period of time.
  • A start time only to indicate when the contact details are valid from.
  • An end time only to indicate that the contact details are only valid until a certain date.
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#guardian" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#guardian"
[1..1] [R] guardianGuardianChoice (GuardianChoice)

A link to the choice of guardian.

GuardianChoice

The choice of a person or organisation guardian.

Used by: Guardian
[1..1] either: GuardianPerson

The guardian person.

... or ... : GuardianOrganization

The guardian organisation.

GuardianPerson

This template class constrains the CDA organization class.

This class is used to carry information about the person who is the patient's guardian.

Used by: Guardian,GuardianChoice
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="PSN" }

Model Attribute Description

The HL7 attribute classCode describes this class as a person.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PSN".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of a person.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[1..*] [R] name (SET<PN>)

Model Attribute Description

The HL7 attribute name provides a name associated with the person who is the patient's guardian.

Implementation in XML Instance

The Person Name Structured with optional Use and optional Valid Time flavour of the PN data type is the recommended format for the guardian's name. This information is carried in the XML element name as follows:

  • The XML element prefix should contain the guardian's title
  • The XML element given should contain the guardian's forenames; there can be as many occurrences of the XML element as required.
  • The XML element family should contain the guardian's surname
  • The XML element suffix may contain any suffix for the guardian

Additionally the XML attribute use of the XML element name should be used to indicate the type of name; the recommended codes to be used are listed below:

Note some of the codes listed are NHS extensions, these are marked with an *

Code Definition
L
Legal
PREFERRED *
Preferred name

Additionally the XML element validTime of the XML element name may be used to indicate the time when the name is valid/was valid for the guardian, some uses are shown below:

  • A point in time when the name details are known to be valid
  • A start and end time
    • To represent the period of time the guardian is/was known by this name.
  • A start time only to indicate when the name is/was valid from for the guardian.
  • An end time only to indicate that the name is/was only valid for the guardian until a certain date.

When no guardian name is available to the sending system to then an appropriate XML attribute nullFlavor may be used to populate the XML element name. The recommended values for the XML attribute nullFlavor are listed below:

nullFlavor Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found (e.g. the guardian was asked but didn't know)
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought (e.g. the guardian was not asked)
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#guardianPerson" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the classname within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#guardianPerson"
GuardianOrganization

This template class constrains the CDA organization class.

This class contains the details of the organisation which is acting as the patient's guardian.

Used by: Guardian,GuardianChoice
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="ORG" }

Model Attribute Description

The HL7 attribute classCode describes this class as an organisation.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "ORG".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of an organisation.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[0..*] addr (SET<AD>)

Model Attribute Description

The HL7 attribute addr provides a contact address for the organisation.

The HL7 attribute addr allows structured and unstructured addresses to be carried in an instance. Only structured addresses are recommended to be used. There are a number of structured forms of addresses. The three shown here are the recommended formats for organisation addresses, they are listed in no particular order.

Implementation in XML Instance

When the structured address in the style of PDS is used then it shall contain five XML elements streetAddressLine:

  • The first XML element streetAddressLine should contain the premises name
  • The second XML element streetAddressLine should contain the number and thoroughfare
  • The third XML element streetAddressLine should contain the locality
  • The fourth XML element streetAddressLine should contain the post town
  • The fifth XML element streetAddressLine should contain the county

The first XML element streetAddressLine or second XML element streetAddressLine and the fourth XML element streetAddressLine are mandated to be populated.

  • The XML element postalCode may be used to carry a postcode
  • The XML element addressKey may be used to carry a PAF key

or the address may use the fully structured address:

  • The XML element houseNumber should contain the house/building number or name
  • The XML element streetName should contain contains the street name
  • The XML element city should contain the city name
  • The XML element county should contain the county
  • The XML element country should contain the country name
  • The XML element postalCode should contain the post code
  • The XML element addressKey should contain the address key

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included:

  • The first XML element streetAddressLine contains the first address line
  • The second XML element streetAddressLine contains the second address line
  • The third XML element streetAddressLine contains the third address line
  • and so on ....

The XML element addr allows an XML attribute use, this should be used to further define the organisation address when required. Only the use values listed below are recommended to be used for organisation addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - may be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
Postal address - Used to send mail.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact address is only for a certain period of time
  • A start time only to indicate when the contact address is valid from
  • An end time only to indicate that the contact address is only valid until a certain date
[0..*] id (SET<II>)

Model Attribute Description

The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which is acting as the patient's guardian. The ODS code should identify the organisation at either the site level or organisation level. Where possible the organisation should be identified at the site level. ODS codes were formerly known as NACS codes. Local identifiers may also be used in addition to ODS codes if required.

Where ODS identifiers are not available then one or more local identifiers may be used.

Implementation in XML Instance

When ODS site code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.2"
  • The XML attribute extension shall contain the ODS site code.

When ODS organisation code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.1"
  • The XML attribute extension shall contain the ODS organisation code.

When using alternative identifiers where the code system can be identified using an OID then the XML element id shall carry the identifiers as follows:

  • The XML attribute root shall contain the OID for the identifying system
  • The XML attribute extension shall contain the author's identifier
[0..*] name (SET<ON>)

Model Attribute Description

The HL7 attribute name uses the description of the organisation associated with the ODS code.

Implementation in XML Instance

The XML element name will carry the description associated with the ODS code carried in the XML attribute extension of the XML element id.

[0..1] standardIndustryClassCode (CE { CWE:GuardianOrganisationType } )

Model Attribute Description

The HL7 attribute standardIndustryClassCode uses a code taken from the GuardianOrganisationType vocabulary to indicate the type of care provider.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element standardIndustryClassCode as follows:

  • The XML attribute code shall contain a code from the GuardianOrganisationType vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.478"
  • The XML attribute displayName shall carry the description associated with the code in the GuardianOrganisationType vocabulary.
[0..*] telecom (SET<TEL>)
Model Attribute Description

The HL7 attribute telecom provides contact details for the organisation in the form of telephone numbers, fax numbers and email addresses.

Implementation in XML Instance

This XML element telecom should be populated as below:

The XML attribute value of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.

  • For a telephone number the actual telephone number would be prefixed with tel:
  • For a fax number the actual fax number would be prefixed with fax:
  • For an email address the actual email address would be prefixed with mailto:

The XML attribute use of the XML element telecom may be used to give further information about the type of contact details contained in the XML attribute value. Only the use values listed below are recommended for an organisation's contact details:

Code Definition
AS Answering service - an automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.
EC
Emergency contact - A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.

The XML element useablePeriod of XML element telecom may be used to indicate when the contact details given are valid, for example to indicate that a telephone number is only for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:

  • A point in time when the contact details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact is only for a certain period of time
  • A start time only to indicate when the contact details are valid from
  • An end time only to indicate that the contact details are only valid until a certain date
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#guardianOrganization" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the classname within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#guardianOrganization"
Birthplace

This template class constrains the CDA Birthplace class.

This class is the role of the patient's birth place.

Used by: Patient
[1..1] [M] classCode (CS { CNE: RoleClass } )
{ Fixed="BIRTHPL" }

Model Attribute Description

The HL7 attribute classCode describes this class as a birth place role.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "BIRTHPL".
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#birthplace" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#birthplace"
[1..1] [M] birthplace (Place)

A link to the birth place.

Place

This template class constrains the CDA Place class.

Details of the actual place which is the place of birth.

Used by: Birthplace
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="PLC" }

Model Attribute Description

The HL7 attribute classCode describes this class as a place.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PLC".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of an organisation.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[0..1] addr (AD)

Model Attribute Description

The HL7 attribute addr uses an address for the patient's birth place.

The HL7 attribute addr allows structured and unstructured addresses to be carried. Only structured addresses are recommended to be used.

Implementation in XML Instance

There are a number of forms of structured address. The three shown here are the recommended formats for patient addresses, they are listed in no particular order.

The XML element addr is populated as follows:

When using the structured address in the style of PDS the XML element addr shall contain five XML elements streetAddressLine:

  • The first XML element streetAddressLine shall contain the premises name
  • The second XML element streetAddressLine shall contain the number and thoroughfare
  • The third XML element streetAddressLine shall contain the locality
  • The fourth XML element streetAddressLine shall contain the post town
  • The fifth XML element streetAddressLine shall contain the county

The first XML element streetAddressLine or the second XML element streetAddressLine and the fourth XML element streetAddressLine are mandatory to be populated.

  • The XML element postalCode can be used to carry a postcode
  • The XML element addressKey can be used to carry a PAF key

When using the fully structured address format then the XML element addr shall be populated as follows:

  • The XML element houseNumber shall contain the house/building number or name
  • The XML element streetName shall contain the street name
  • The XML element city shall contain the city name
  • The XML element county shall contain the county
  • The XML element country shall contain the country name
  • The XML element postalCode shall contain the postcode
  • The XML element addressKey shall contain the address key

Note that unpopulated XML elements should not be present.

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included.

  • The first XML element streetAddressLine shall contain the first address line
  • The second XML element streetAddressLine shall contain the second address line
  • The third XML element streetAddressLine shall contain the third address line
  • and so on ....

Note that unpopulated XML elements should not be present.

The XML element addr also allows an XML attribute use and this should be used to further define the patient address type when required. Only the use values listed below are recommended to be used for patient addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - A temporary address; may be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
Postal address - Used to send mail.
H
Home address - The person's home address; attempted contacts for business purposes might intrude privacy and chances are one will contact family or other household members instead of the person one wishes to call. Typically used with urgent cases, or if no other contacts are available.
HP
The primary home address - An address to reach a person after business hours.
HV
A vacation home - An address to reach a person while on vacation.

When the XML attribute use of the XML element addr contains the value "PHYS" then the following two XML elements of the XML element addr may be populated.

  • The XML element desc of the XML element addr may contain a description of the address; this may be used for things like directions for the address.
  • The XML element additionalLocator of the XML element addr may contain additional location information such as longitude and latitude coordinates.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times for an address:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours of an office for a work address
    • Using dates for indicating a contact address is only for a certain period of time.
  • A start time only to indicate when the contact address is valid from.
  • An end time only to indicate that the contact address is only valid until a certain date.
[0..1] name (EN)

Model Attribute Description

The HL7 attribute name is used when the place has a name.

Implementation in XML Instance

The XML element name shall contain a string which is the name of the place.

[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#birthplace" }
Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the classname within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:
  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#birthplace"
LanguageCommunication

This template class constrains the CDA LanguageCommunication class.

This class is used to describe information about the patient's languages, their mode of communication and proficiency in that language, and whether it is their preferred language.

Used by: Patient
[0..1] languageCode (CS { CNE:HumanLanguage } )

Model Attribute Description

The HL7 attribute languageCode uses a code taken from the HL7 HumanLanguage vocabulary to describe a language used by the patient.

Implementation in XML Instance

The Coded Only data type flavour of Simple Value data type is used to carry this information as follows:

  • The XML code attribute of the XML code element shall contain a code from the HL7 HumanLanguage vocabulary.
[0..1] modeCode (CE { CWE:LanguageAbilityMode } )

Model Attribute Description

The HL7 attribute modeCode uses a code taken from the HL7 LanguageAbilityMode vocabulary or an alternative vocabulary to describe: the mode the patient can communicate in the language stated in the HL7 attribute languageCode.

Implementation in XML Instance

When the HL7 LanguageAbilityMode vocabulary is used then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element modeCode as follows:

  • The XML attribute code shall contain a code from table below
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.5.60"
  • The XML attribute displayName shall carry the displayName associated with the code in the table below
Code DisplayName
ESGN
Expressed signed
ESP Expressed spoken
EWR Expressed written
RSGN Received signed
RSP Received spoken
RWR Received written

When an alternative vocabulary is used and an OID is available then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element modeCode as follows:

  • The XML attribute code shall contain a code from the alternative vocabulary
  • The XML attribute codeSystem shall contain the OID for the alternative vocabulary
  • The XML attribute displayName shall carry the display name or description associated with the code in the alternative vocabulary

When an alternative vocabulary is used and an OID is not available then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element modeCode as follows:

  • The XML attribute code shall contain a code from the alternative vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.400"
  • The XML attribute displayName shall carry the display name or description associated with the code in the alternative vocabulary
[0..1] preferenceInd (BL)

Model Attribute Description

A flag used to indicate if the language stated in languageCode is preferred by the patient.

Implementation in XML Instance

When sending a Boolean value, the XML attribute value of the XML element preferenceInd should carry true or false.

The XML element preferenceInd can carry an XML element nullFlavor instead of true or false to allow assertion of things like "patient was not asked".

The recommended values for the XML attribute nullFlavor are listed below

nullFlavor Definition
UNK Unknown - A proper value is applicable, but not known
ASKU Asked but unknown - Information was sought but not found (e.g., patient was asked but didn't know)
NAV Temporarily unavailable - Information is not available at this time but it is expected that it will be available later.
NASK Not asked - This information has not been sought (e.g., patient was not asked)
MSK Masked - There is information on this item available but it has not been provided by the sender due to security, privacy or other reasons.

There may be an alternate mechanism for gaining access to this information.

[0..1] proficiencyLevelCode (CE { CWE:LanguageAbilityProficiency } )

Model Attribute Description

The HL7 attribute proficiencyLevelCode uses a code taken from the HL7 LanguageAbilityProficiency vocabulary or an alternative vocabulary to describe the patient's proficiency to communicate in the mode stated in the HL7 attribute modeCode, for the language stated in the HL7 attribute languageCode.

Implementation in XML Instance

When the HL7 vocabulary LanguageAbilityProficiency is used then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element proficiencyLevelCode as follows:

  • The XML attribute code shall contain a code from the table below
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.5.61"
  • The XML attribute displayName shall carry the displayName associated with the code in the table below
Code DisplayName
E
Excellent
F
Fair
G
Good
P
Poor

When an alternative vocabulary is used and an OID is available then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element proficiencyLevelCode as follows:

  • The XML attribute code shall contain a code from the alternative vocabulary
  • The XML attribute codeSystem shall contain the OID for the alternative vocabulary
  • The XML attribute displayName shall carry the display name or description associated with the code in the alternative vocabulary

When an alternative vocabulary is used and an OID is not available then:

The Coded Plain data type flavour of Coded with Equivalents (CE) shall be used to carry this information in the XML element proficiencyLevelCode as follows:

  • The XML attribute code shall contain a code from the alternative vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.401"
  • The XML attribute displayName shall carry the display name or description associated with the code in the alternative vocabulary
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#languageCommunication" }

Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:

  • The XML root attribute is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML extension attribute is fixed to "COCD_TP145201GB02#languageCommunication".
Organization

This template class constrains the CDA organization class.

This class details the organisation which provides/provided care to the patient.

Used by: OrganizationPartOf,PatientRole
[1..1] [M] classCode (CS { CNE: EntityClass } )
{ Fixed="ORG" }

Model Attribute Description

The HL7 attribute classCode describes this class as an organisation.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "ORG".
[1..1] [M] determinerCode (CS { CNE: EntityDeterminer } )
{ Fixed="INSTANCE" }

Model Attribute Description

The HL7 attribute determinerCode describes this class as an instance of an organisation.

Implementation in XML Instance

  • The XML attribute determinerCode is fixed to "INSTANCE".
[0..1] addr (AD)

Model Attribute Description

The HL7 attribute addr provides a contact address for the organisation.

The HL7 attribute addr allows structured and unstructured addresses to be carried in an instance. Only structured addresses are recommended to be used. There are a number of structured forms of addresses. The three shown here are the recommended formats for organisation addresses, they are listed in no particular order.

Implementation in XML Instance

When the structured address in the style of PDS is used then it shall contain five XML elements streetAddressLine:

  • The first XML element streetAddressLine should contain the premises name
  • The second XML element streetAddressLine should contain the number and thoroughfare
  • The third XML element streetAddressLine should contain the locality
  • The fourth XML element streetAddressLine should contain the post town
  • The fifth XML element streetAddressLine should contain the county

The first XML element streetAddressLine or second XML element streetAddressLine and the fourth XML element streetAddressLine are mandated to be populated.

  • The XML element postalCode may be used to carry a postcode
  • The XML element addressKey may be used to carry a PAF key

or the address may use the fully structured address:

  • The XML element houseNumber should contain the house/building number or name
  • The XML element streetName should contain contains the street name
  • The XML element city should contain the city name
  • The XML element county should contain the county
  • The XML element country should contain the country name
  • The XML element postalCode should contain the post code
  • The XML element addressKey should contain the address key

Alternatively the structured address may contain just a series of XML elements streetAddressLine populated in the correct order to render as a postal address with as much information as available included:

  • The first XML element streetAddressLine contains the first address line
  • The second XML element streetAddressLine contains the second address line
  • The third XML element streetAddressLine contains the third address line
  • and so on ....

The XML element addr allows an XML attribute use, this should be used to further define the organisation address when required. Only the use values listed below are recommended to be used for organisation addresses.

Code
Definition
WP Work place - An office address. First choice for business related contacts during business hours.
TMP Temporary address - may be good for visit or mailing.
PHYS Physical visit address - Used primarily to visit an address.
PST
Postal address - Used to send mail.

The XML element useablePeriod of XML element addr can be used to indicate some of the following types of valid times:

  • A point in time when the contact address details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact address is only for a certain period of time
  • A start time only to indicate when the contact address is valid from
  • An end time only to indicate that the contact address is only valid until a certain date
[1..1] [M] id (II)

Model Attribute Description

The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which provides/provided care to the patient. The ODS code should identify the organisation at either the site level or organisation level. Where possible the organisation should be identified at the site level. ODS codes were formerly known as NACS codes.

Implementation in XML Instance

When ODS site code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.2"
  • The XML attribute extension shall contain the ODS site code.

When ODS organisation code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.1"
  • The XML attribute extension shall contain the ODS organisation code.
[1..1] [M] name (ON)

Model Attribute Description

The HL7 attribute name uses the description of the organisation associated with the ODS code.

Implementation in XML Instance

The XML element name will carry the description associated with the ODS code carried in the XML attribute extension of the XML element id.

[1..1] [M] standardIndustryClassCode (CV { CNE:CDAOrganizationProviderType } )

Model Attribute Description

The HL7 attribute standardIndustryClassCode uses a code taken from the CDAOrganizationProviderType vocabulary to indicate the type of care provider.

The only use currently for this attribute is to indicate that the organisation is the patient's registered GP practice.

Implementation in XML Instance

The Coded Plain data type flavour of Coded Value (CV) shall be used to carry this information in the XML element standardIndustryClassCode as follows:

  • The XML attribute code shall contain a code from the CDAOrganizationProviderType vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.289"
  • The XML attribute displayName shall carry the description associated with the code in the CDAOrganizationProviderType vocabulary.
[0..*] telecom (SET<TEL>)

Model Attribute Description

The HL7 attribute telecom provides contact details for the organisation in the form of telephone numbers, fax numbers and email addresses.

Implementation in XML Instance

This XML element telecom should be populated as below:

The XML attribute value of the XML element telecom should contain the telephone / fax number or an email address prefixed by the type of contact and a colon.

  • For a telephone number the actual telephone number would be prefixed with tel:
  • For a fax number the actual fax number would be prefixed with fax:
  • For an email address the actual email address would be prefixed with mailto:

The XML attribute use of the XML element telecom may be used to give further information about the type of contact details contained in the XML attribute value. Only the use values listed below are recommended for an organisation's contact details:

Code Definition
AS Answering service - an automated answering machine used for less urgent cases and if the main purpose of contact is to leave a message or access an automated announcement.
EC
Emergency contact - A contact specifically designated to be used for emergencies. This is the first choice in emergencies, independent of any other use codes.

The XML element useablePeriod of XML element telecom may be used to indicate when the contact details given are valid, for example to indicate that a telephone number is only for office hours (9am to 5 pm). It can be used to indicate some of the following types of valid times:

  • A point in time when the contact details are valid
  • A start and end time
    • Just including hours and minutes to indicate opening hours
    • Using dates for indicating a contact is only for a certain period of time
  • A start time only to indicate when the contact details are valid from
  • An end time only to indicate that the contact details are only valid until a certain date
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#providerOrganization" }

Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:

  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145201GB02#providerOrganization".
[0..1] playedOrganizationPartOf (OrganizationPartOf)

A link to the whole organisation.

OrganizationPartOf

This template class constrains the CDA OrganizationPartOf class.

This class is used to carry information about the organisation the provider organisation is part of.

Used by: Organization
[1..1] [M] classCode (CS { CNE: RoleClass } )
{ Fixed="PART" }

Model Attribute Description

The HL7 attribute classCode describes this class as a part role.

Implementation in XML Instance

  • The XML attribute classCode is fixed to "PART".
[0..1] code (CV { CWE:CDAOrganizationType } )

Model Attribute Description

The HL7 attribute code uses a code from the CDAOrganizationType vocabulary to describe the relationship between the patient and the named person.

Implementation in XML Instance

The Coded Plain flavour of the Coded Value (CV) data type shall be used to carry this information in the XML element code as follows:

  • The XML attribute code shall contain a code from the GuardianRoleType vocabulary
  • The XML attribute codeSystem shall contain the OID "2.16.840.1.113883.2.1.3.2.4.17.191"
  • The XML attribute displayName shall carry the name associated with the code
[0..1] effectiveTime (IVL<TS>)

Model Attribute Description

The HL7 attribute effectiveTime defines the time period during which the the provider organisation is part of the larger organisation.

Implementation in XML Instance

The Interval of Points in Time data type flavour carries this information in the XML element effectiveTime using the value attributes of the of the XML elements low and high.

The date range shall be carried as follows:

The XML attribute value of the XML elements low and high, shall be populated with a time stamp in the format yyyymmddhhmmss[+|-ZZzz] where:

  • yyyy is the year
  • mm is the month
  • dd is the day
  • hh is the hour
  • mm is the minute
  • ss is seconds
  • [+|-ZZzz] is the time zone offset in hours and minutes

Sections from the right of this representation may be left off when the sending system does not record to this level of accuracy. When hours are present, the time zone offset must also be present.

The 'start date' shall be present, and only where appropriate the 'end date' can be included. The Time Interval Complete data type shall be used:

  • The XML attribute value of the XML element low shall be populated with a 'start date' time stamp
  • The XML attribute value of the XML element high shall be populated with an 'end date' time stamp

Note, where the provider organisation is still part of the other organisation, then the XML element high should not be populated, to reflect that there is no 'end date' time stamp in this situation.

The XML attribute value of the XML elements low and high should be populated to the level of detail that is available on the sending system.

[0..*] id (SET<II>)

Model Attribute Description

The HL7 attribute id uses an ODS code as an identifier that uniquely identifies the organisation which provides/provided care to the patient. The ODS code should identify the organisation at either the site level or organisation level. Where possible the organisation should be identified at the site level. ODS codes were formerly known as NACS codes. Local identifiers may also be used in addition to ODS codes if required.

Where ODS identifiers are not available then one or more local identifiers may be used.

Implementation in XML Instance

When ODS site code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.2"
  • The XML attribute extension shall contain the ODS site code.

When ODS organisation code is used then the XML element id is populated in the following way:

  • The XML attribute root shall contain an OID with the value "2.16.840.1.113883.2.1.3.2.4.19.1"
  • The XML attribute extension shall contain the ODS organisation code.

When using alternative identifiers where the code system can be identified using an OID then the XML element id shall carry the identifiers as follows:

  • The XML attribute root shall contain the OID for the identifying system
  • The XML attribute extension shall contain the author's identifier

[0..1] statusCode (CS { CNE:RoleStatus } )

Model Attribute Description

The HL7 attribute statusCode uses a code to describe the status of the role.

Implementation in XML Instance

The Coded Simple (CS) data type flavour shall be used to carry this information in the XML element statusCode as follows:

  • The XML attribute code of the XML element statusCode shall contain a code from the RoleStatus vocabulary
[1..1] [M] templateId (II)
{ Fixed="COCD_TP145201GB02#playedOrganizationPartOf" }

Model Attribute Description

The HL7 attribute templateId provides a unique identifier for the template and the class name within that template. This is used to identify how the CDA standard has been constrained for NHS use.

Implementation in XML Instance

The Identifier External data type flavour is used to carry this information in the XML element templateId as follows:

  • The XML attribute root is fixed to the OID "2.16.840.1.113883.2.1.3.2.4.18.2"
  • The XML attribute extension is fixed to "COCD_TP145230GB02#playedOrganisationPartOf"
[0..1] wholeOrganization (Organization)

A link to the organisation that this is a part of.